X Twitter Profile Scraper

Scrape public X/Twitter profile details for influencer discovery, competitor research, social listening, lead enrichment, and AI-agent workflows.

What It Extracts

This actor accepts X/Twitter handles or profile URLs and returns one normalized profile row per public account. It uses provider-backed public data, so it does not require user cookies, browser sessions, login credentials, or an X developer account.

Field group	Included fields
Identity	username, name, userId, profileUrl
Profile copy	bio, location, websiteUrl, businessLabel
Media	avatarUrl, bannerUrl
Verification	isVerified, isBlueVerified, isProtected
Audience metrics	followersCount, followingCount, tweetCount, mediaCount, listedCount, likesCount
Account context	accountCreatedAt, pinnedTweetIds
Optional tweets	tweetId, tweetUrl, text, createdAt, engagement counts, hashtags, mentions, urls, mediaUrls
Run telemetry	provider, scrapedAt, OUTPUT, RUN_SUMMARY

When To Use It

Use this actor when you need clean public X/Twitter profile data for:

• Influencer and creator vetting
• Competitor account monitoring
• Brand and executive social profile enrichment
• Lead research for sales, recruiting, and partnerships
• Social media benchmarking
• AI-agent research tools that need predictable profile JSON
• CRM enrichment from a list of X/Twitter handles

Use the optional includeTweets setting when you want public tweet examples for context. The upstream public endpoint returns roughly the top public tweets surfaced for a profile, not a complete chronological archive.

When Not To Use It

This actor does not unlock private accounts, deleted posts, DMs, private follower graphs, hidden email addresses, or login-only data. It does not scrape complete follower lists. For follower or following graph data, use a dedicated X/Twitter followers actor. For keyword search across X, use an X/Twitter search scraper.

Input

The main input is profiles, a line-separated list of handles or URLs.

{
  "profiles": ["openai", "@apify", "https://x.com/levelsio"],
  "includeTweets": false,
  "maxTweetsPerProfile": 10,
  "dedupeProfiles": true,
  "providerOrder": "auto"
}

For a richer profile plus tweet context run:

{
  "profiles": ["openai", "apify"],
  "includeTweets": true,
  "maxTweetsPerProfile": 5
}

Output

Profile rows are intentionally flat and MCP-friendly:

{
  "recordType": "profile",
  "inputProfile": "openai",
  "userId": "4398626122",
  "username": "OpenAI",
  "name": "OpenAI",
  "bio": "Creating safe AGI that benefits all of humanity.",
  "profileUrl": "https://x.com/OpenAI",
  "location": "San Francisco, CA",
  "websiteUrl": "https://openai.com",
  "isBlueVerified": true,
  "followersCount": 10000000,
  "followingCount": 3,
  "tweetCount": 9000,
  "accountCreatedAt": "2015-12-11T20:29:15.000Z",
  "provider": "scrapecreators",
  "scrapedAt": "2026-06-12T12:00:00.000Z"
}

Optional tweet rows use the same dataset so agents can page one output stream:

{
  "recordType": "tweet",
  "inputProfile": "openai",
  "username": "OpenAI",
  "profileUrl": "https://x.com/OpenAI",
  "tweetId": "1234567890123456789",
  "tweetUrl": "https://x.com/OpenAI/status/1234567890123456789",
  "text": "Announcing a new research update.",
  "createdAt": "2026-06-12T12:00:00.000Z",
  "likeCount": 1000,
  "viewCount": 50000,
  "provider": "scrapecreators",
  "scrapedAt": "2026-06-12T12:00:01.000Z"
}

The actor also writes OUTPUT and RUN_SUMMARY to the key-value store with saved counts, charged counts, provider status codes, provider fallback usage, warnings, and stop reason.

Pricing

This actor uses pay-per-event pricing:

Event	Price
Actor start	$0.00005
Public X/Twitter profile saved	$0.007
Optional public profile tweet saved	$0.0005

Example: 100 profile-only rows cost about $0.70 plus the tiny actor start event. Ten profiles with five optional tweets each cost about $0.095.

The run status message prints the maximum possible charge before data collection starts, and the final summary prints the actual charged profile and tweet events.

Reliability

The actor tries ScrapeCreators first by default because its X profile endpoint is rich and cost efficient. If SociaVault credentials are configured, the actor can fall back to SociaVault for profile and tweet endpoints. You can force the provider order with providerOrder during validation.

Provider errors, missing profiles, empty responses, and invalid input are written to OUTPUT and RUN_SUMMARY with warnings instead of crashing silently. Dataset writes use a defensive fallback so one malformed optional field does not destroy the whole run.

API And MCP Use

This actor is designed for Apify API calls, scheduled tasks, and hosted Apify MCP usage. The input schema uses clear field names and defaults, and the dataset schema keeps profile rows flat so AI agents can inspect, filter, and chain the records into other workflows.

Use via API:

apify call khadinakbar/x-twitter-profile-scraper \
  --input='{"profiles":["openai","apify"],"includeTweets":false}'

Use from an agent when the user asks for public X/Twitter account metadata, influencer vetting, profile enrichment, or social account benchmarking. Do not use it for keyword tweet search, follower graph scraping, private account data, or hidden contact discovery.

Limits

• Public profile data only
• No user cookies required or accepted
• Optional tweet rows are public top tweets surfaced by the provider, not a complete archive
• Maximum 100 input profiles per run
• Maximum 100 optional tweets per profile
• Field availability depends on what public X/Twitter data and the upstream provider expose at run time

Legal

This actor is intended for lawful collection and analysis of public web data. You are responsible for using the exported data in compliance with applicable laws, platform terms, privacy obligations, and your own internal policies.